Changes

Users can know pass custom --mode other than production and development, like staging or anything else etc.

Within Astro, how do we actually tell in we're in dev or prod state now?

For astro dev, it'll always be in the dev state. It's not possible to be in a prod state as it may break existing code, like HMR and stuff (which is also a restriction in Vite)

For astro build, it'll be prod state by default, unless the user passes --dev which Astro will then switch to a dev state.

In other parts of the codebase, there's also the concept of runtimeMode which contains this state as either "development" or "production" values only.

Future coding style

If we want to check the prod or dev state, we should no longer rely on mode as that's no longer relevant. We can check via these states instead:

1. viteResolvedConfig.isProduction
2. runtimeMode
3. process.env.NODE_ENV === 'production'
4. import.meta.env.PROD and import.meta.env.DEV

Testing

Added a new test to verify that it works.

Docs

TBA. The --dev flag will require docs.